Profile Unity application performance on Android devices
Introduction
Analyzing the sample application
Preparation
Inside the code
Profiling
Collect performance data
Using the Unity Analyzer
Next Steps

  Log an issue

  Fork and edit

  Discuss on Discord

About this Learning Path

Skill level:  Introductory
Reading time:  40 min
Last updated:  24 Aug 2026
Skill level:
  Introductory
Reading time:
  40 min
Last updated:
  24 Aug 2026
Author:Joshua Marshall-Law
Arm IP:Cortex-A
Tags: Performance and Architecture Android Unity csharp
Author:
  • Joshua Marshall-Law
Arm IP:
Cortex-A
Tags:
Performance and Architecture Android Unity csharp

Who is this for?

Unity developers wanting to analyze the performance of their apps on Android devices

What will you learn?

Upon completion of this Learning Path, you will be able to:

  • Deploy to Android
  • Profile code running on an Android device
  • Analyze performance data

Prerequisites

Before starting, you will need the following:

  • Recent Android device, such as a mobile phone or tablet
  • Desktop computer capable of running Unity
  • Basic knowledge of Unity and programming concepts
  • The setup described in the Learning Path Get started with Unity on Android

Summary

AI-assisted

This summary was drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.

Close
?
You’ll deploy a Unity collision sample to an Android device, collect performance data, and compare unoptimized and Arm Neon code. First, you’ll create a URP project, import and deploy the sample, and examine the Plain, Burst, and Neon modes. Then, you’ll use Unity Profiler to record and inspect frames. You’ll also use Profile Analyzer to load, select, and compare the Plain and Neon recordings.

Frequently asked questions

AI-assisted

These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.

Close
?
Do I need to create a new Unity project before importing the sample?
Yes. In Unity Hub, select New Project, select the 3D (URP) Core template, and create a blank project before you import the sample.
Which tool should I use to examine results?
Use the Profiler to collect data and inspect specific frames. To use Profile Analyzer, open the Profiler window, load the recording there, and select Pull Data to analyze or compare datasets.
Which sample modes should I record for comparison?
Record the unoptimized Plain mode and the optimized Neon mode. You can also inspect Burst mode to see how its auto-vectorized code differs.
How do I compare the Plain and Neon recordings?
Compare recordings from the unoptimized Plain mode and the optimized Neon mode. Use the Profiler and Profile Analyzer to examine differences in frame timing and function execution.
What should I check if the Android device or app doesn't appear for profiling?
Confirm the app builds and deploys to the Android device using the steps from the Get started with Unity on Android Learning Path. After confirming, run the app on the device before recording. If no data appears, re-verify deployment and that the device is actively running the sample.
Next